Software Engineering—Principles and Practices by Rajesh Narang

Author:Rajesh Narang [Narang, Rajesh]
Language: eng
Format: azw3
Published: 2015-07-26T16:00:00+00:00

8.2.1 Structure of Application Testing

A sample structure of the application testing is given as follows and it can be adopted to test Software:

• Requirement traceability: State stakeholders expects an application to meet its intended requirements so the testing team should test all the functional and non-functional requirements beforehand. The system development team must ensure that the documentation for the requirement specifications includes traceability of each requirement, i.e., source of requirement within it.

• List of Testing Artefacts: All the artefacts such as mandatory and optional services, static and dynamic queries, reports, etc., which are tested should be mentioned.

• Testing Timelines: The overall testing duration and resources allocated for the testing should be specified.

• Testing reporting method: The results of the test must be systematically recorded so that it is possible to audit the testing process to check its correctness.

• Availability of Testing Environment: The testing environment including hardware, system Software, and application should be made available by the customers to test team. The team needs to specify hardware and system Software utilization at normal and peak transactions and concurrent user load to enable the customers determine their resource requirements for full roll out.

8.2.2 Program Inspection Process

As the name suggests, Program Inspection is a review conducted to identify the defects in a program. But it is not intended to find discrepancies in the design. Other reviews are conducted for this purpose. There are quality reviews where the objective is to evaluate the schedule, costs, progress against defined milestones, or to ascertain whether the Software will meet the organizational goals or not. But in program review, the objective is to find logical errors and anomalies in code which may invoke error and exceptional conditions or non-compliances to organizational or project standards.

The role of a facilitator is to organize the inspection process. A facilitator selects the inspection team, books a conference room, and arranges for the material and its specifications that have to be inspected.

As per Sommervile, the roles and responsibilities of different inspection members are as follows:

• Code writer: A code writer’s job is to develop the program, documents, and fix defects found during the inspection process.

• Evaluator: An evaluator identifies errors, omissions, anomalies, and inconsistencies in programs and then documents them. He may also point out additional broader issues which are not included in the scope of evaluation. There can be one or more evaluators.

• Presenter: This role makes presentation of the code or document to entire team.

• Proceeding recorder: The role of a proceeding recorder is to write the minutes of the meeting including the decision and action points of the discussion held during inspection meeting.

• Facilitator: This role moderates, manages, and facilitates the meeting. He reports the results of inspections to the person next to him in hierarchy, say chief moderator.

• Senior facilitator: A senior facilitator is responsible for bringing improvements in the process of inspection, checklist, standards building, or corrections.

The code under inspection is given to the evaluator and other team members during overview stage wherein the code writer describes the purpose and intention of the code.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.